Methods and apparatus for providing hypervisor level data services for server virtualization

ABSTRACT

A cross-host multi-hypervisor system, including a plurality of host sites, each site including at least one hypervisor, each of which includes at least one virtual server, at least one virtual disk that is read from and written to by the at least one virtual server, a tapping driver in communication with the at least one virtual server, which intercepts write requests made by any one of the at least one virtual server to any one of the at least one virtual disk, and a virtual data services appliance, in communication with the tapping driver, which receives the intercepted write requests from the tapping driver, and which provides data services based thereon, and a data services manager for coordinating the virtual data services appliances at the site, and a network for communicatively coupling the plurality of sites, wherein the data services managers coordinate data transfer across the plurality of sites via the network.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application claims priority under 35 U.S.C. § 120 as a continuationof U.S. application Ser. No. 13/175,892, titled METHODS AND APPARATUSFOR PROVIDING HYPERVISOR LEVEL DATA SERVICES FOR SERVER VIRTUALIZATION,filed on Jul. 4, 2011, which claims priority under 35 U.S.C. § 120 as acontinuation-in-part of U.S. application Ser. No. 13/039,446, titledMETHODS AND APPARATUS FOR PROVIDING HYPERVISOR LEVEL DATA SERVICES FORSERVER VIRTUALIZATION, filed on Mar. 3, 2011, which claims priorityunder 35 U.S.C. § 119(e) to U.S. Provisional Application No. 61/314,589,titled METHODS AND APPARATUS FOR PROVIDING HYPERVISOR LEVEL DATASERVICES FOR SERVER VIRTUALIZATION, filed on Mar. 17, 2010, each ofwhich is incorporated herein by reference in their entireties.

FIELD OF THE INVENTION

The present invention relates to virtual server computing environments.

BACKGROUND OF THE INVENTION

Data center virtualization technologies are now well adopted intoinformation technology infrastructures. As more and more applicationsare deployed in a virtualized infrastructure, there is a growing needfor recovery mechanisms to support mission critical applicationdeployment, while providing complete business continuity and disasterrecovery.

Virtual servers are logical entities that run as software in a servervirtualization infrastructure, referred to as a “hypervisor”. Examplesof hypervisors are VMWARE® ESX manufactured by VMware, Inc. of PaloAlto, Calif., HyperV manufactured by Microsoft Corporation of Redmond,Wash., XENSERVER® manufactured by Citrix Systems, Inc. of FortLauderdale, Fla., Redhat KVM manufactured by Redhat, Inc. of Raleigh,N.C., and Oracle VM manufactured by Oracle Corporation of RedwoodShores, Calif. A hypervisor provides storage device emulation, referredto as “virtual disks”, to virtual servers. Hypervisor implements virtualdisks using back-end technologies such as files on a dedicated filesystem, or raw mapping to physical devices.

As distinct from physical servers that run on hardware, virtual serversrun their operating systems within an emulation layer that is providedby a hypervisor. Although virtual servers are software, neverthelessthey perform the same tasks as physical servers, including runningserver applications such as database applications, customer relationmanagement applications and MICROSOFT EXCHANGE SERVER®. Mostapplications that run on physical servers are portable to run on virtualservers. As distinct from virtual desktops that run client sideapplications and service individual users, virtual servers runapplications that service a large number of clients.

As such, virtual servers depend critically on data services for theiravailability, security, mobility and compliance requirements. Dataservices include inter alia continuous data protection, disasterrecovery, remote replication, data security, mobility, and dataretention and archiving policies.

Conventional replication and disaster recovery systems were not designedto deal with the demands created by the virtualization paradigm. Mostconventional replication systems are not implemented at the hypervisorlevel, with the virtual servers and virtual disks, but instead areimplemented at the physical disk level. As such, these conventionalsystems are not fully virtualization-aware. In turn, the lack ofvirtualization awareness creates an operational and administrativeburden, and a certain degree of inflexibility.

It would thus be of advantage to have data services that are fullyvirtualization-aware.

SUMMARY OF THE DESCRIPTION

Aspects of the present invention relate to a dedicated virtual dataservice appliance (VDSA) within a hypervisor that can provide a varietyof data services. Data services provided by the VDSA include inter aliareplication, monitoring and quality of service. The VDSA is fullyapplication-aware.

In an embodiment of the present invention, a tapping filter driver isinstalled within the hypervisor kernel. The tapping driver hasvisibility to I/O requests made by virtual servers running on thehypervisor.

A VDSA runs on each physical hypervisor. The VDSA is a dedicated virtualserver that provides data services; however, the VDSA does notnecessarily reside in the actual I/O data path. When a data serviceprocesses I/O asynchronously, the VDSA receives the data outside thedata path.

Whenever a virtual server performs I/O to a virtual disk, the tappingdriver identifies the I/O requests to the virtual disk. The tappingdriver copies the I/O requests, forwards one copy to the hypervisor'sbackend, and forwards another copy to the VDSA.

Upon receiving an I/O request, the VDSA performs a set of actions toenable various data services. A first action is data analysis, toanalyze the data content of the I/O request and to infer informationregarding the virtual server's data state. E.g., the VDSA may infer theoperating system level and the status of the virtual server. Thisinformation is subsequently used for reporting and policy purposes.

A second action, optionally performed by the VDSA, is to store each I/Owrite request in a dedicated virtual disk for journaling. Since all I/Owrite requests are journaled on this virtual disk, the virtual diskenables recovery data services for the virtual server, such as restoringthe virtual server to an historical image.

A third action, optionally performed by the VDSA, is to send I/O writerequests to different VDSAs, residing on hypervisors located atdifferent locations, thus enabling disaster recovery data services.

The hypervisor architecture of the present invention scales to multiplehost sites, each of which hosts multiple hypervisors. The scalingflexibly allows for different numbers of hypervisors at different sites,and different numbers of virtual services and virtual disks withindifferent hypervisors. Each hypervisor includes a VDSA, and each siteincludes a data services manager to coordinate the VSDA's at the site,and across other sites.

Embodiments of the present invention enable flexibly designating one ormore virtual servers within one or more hypervisors at a site as being avirtual protection group, and flexibly designating one or morehypervisors, or alternatively one or more virtual servers within one ormore hypervisors at another site as being a replication target for thevirtual protection group. Write order fidelity is maintained for virtualprotection groups. A site may comprise any number of source and targetvirtual protection groups. A virtual protection group may have more thanone replication target. The number of hypervisors and virtual serverswithin a virtual protection group and its replication target are notrequired to be the same.

There is thus provided in accordance with an embodiment of the presentinvention a cross-host multi-hypervisor system, including a plurality ofhost sites, each site including at least one hypervisor, each of whichincludes at least one virtual server, at least one virtual disk that isread from and written to by the at least one virtual server, a tappingdriver in communication with the at least one virtual server, whichintercepts write requests made by any one of the at least one virtualserver to any one of the at least one virtual disk, and a virtual dataservices appliance, in communication with the tapping driver, whichreceives the intercepted write requests from the tapping driver, andwhich provides data services based thereon, and a data services managerfor coordinating the virtual data services appliances at the site, and anetwork for communicatively coupling the plurality of sites, wherein thedata services managers coordinate data transfer across the plurality ofsites via the network.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be more fully understood and appreciated fromthe following detailed description, taken in conjunction with thedrawings in which:

FIG. 1 is a simplified block diagram of a hypervisor architecture thatincludes a tapping driver and a virtual data services appliance, inaccordance with an embodiment of the present invention;

FIG. 2 is a simplified data flow chart for a virtual data servicesappliance, in accordance with an embodiment of the present invention;

FIG. 3 is a simplified block diagram of a virtual replication system, inaccordance with an embodiment of the present invention;

FIG. 4 is a simplified block diagram of a cross-host multiple hypervisorsystem that includes data services managers for multiple sites that havemultiple hypervisors, in accordance with an embodiment of the presentinvention;

FIG. 5 is a user interface screenshot of bi-directional replication ofvirtual protection groups, in accordance with an embodiment of thepresent invention;

FIG. 6 is a user interface screenshot of assignment of a replicationtarget for a virtual protection group, in accordance with an embodimentof the present invention; and

FIG. 7 is an example an environment for the system of FIG. 4, inaccordance with an embodiment of the present invention.

LIST OF APPENDICES

Appendix I is an application programming interface for virtualreplication site controller web services, in accordance with anembodiment of the present invention;

Appendix II is an application programming interface for virtualreplication host controller web services, in accordance with anembodiment of the present invention;

Appendix III is an application programming interface for virtualreplication protection group controller web services, in accordance withan embodiment of the present invention;

Appendix IV is an application programming interface for virtualreplication command tracker web services, in accordance with anembodiment of the present invention; and

Appendix V is an application programming interface for virtualreplication log collector web services, in accordance with an embodimentof the present invention.

DETAILED DESCRIPTION

Aspects of the present invention relate to a dedicated virtual dataservices appliance (VDSA) within a hypervisor, which is used to providea variety of hypervisor data services. Data services provided by a VDSAinclude inter alia replication, monitoring and quality of service.

Reference is made to FIG. 1, which is a simplified block diagram of ahypervisor architecture that includes a tapping driver and a VDSA, inaccordance with an embodiment of the present invention. Shown in FIG. 1is a hypervisor 100 with three virtual servers 110, three virtual disks120, an I/O backend 130 and a physical storage array 140. Hypervisor 100uses a single physical server, but runs multiple virtual servers 110.Virtual disks 120 are a storage emulation layer that provide storage forvirtual servers 110. Virtual disks 120 are implemented by hypervisor 100via I/O backend 130, which connects to physical disk 140.

Hypervisor 100 also includes a tapping driver 150 installed within thehypervisor kernel. As shown in FIG. 1, tapping driver 150 resides in asoftware layer between virtual servers 110 and virtual disks 120. Assuch, tapping driver 150 is able to access I/O requests performed byvirtual servers 110 on virtual disks 120. Tapping driver 150 hasvisibility to I/O requests made by virtual servers 110.

Hypervisor 100 also includes a VDSA 160. In accordance with anembodiment of the present invention, a VDSA 160 runs on a separatevirtual server within each physical hypervisor. VDSA 160 is a dedicatedvirtual server that provides data services via one or more data servicesengines 170. However, VDSA 160 does not reside in the actual I/O datapath between I/O backend 130 and physical disk 140. Instead, VDSA 160resides in a virtual I/O data path.

Whenever a virtual server 110 performs I/O on a virtual disk 120,tapping driver 150 identifies the I/O requests that the virtual servermakes. Tapping driver 150 copies the I/O requests, forwards one copy viathe conventional path to I/O backend 130, and forwards another copy toVDSA 160. In turn, VDSA 160 enables the one or more data servicesengines 170 to provide data services based on these I/O requests.

Reference is made to FIG. 2, which is a simplified data flow chart for aVDSA, in accordance with an embodiment of the present invention. Shownin FIG. 2 are an I/O receiver 210, a hash generator 220, a TCPtransmitter 230, a data analyzer and reporter 240, a journal manager 250and a remote VDSA 260. Remote VDSA 260 resides on different physicalhardware, at a possibly different location.

As shown in FIG. 2, I/O receiver 210 receives an intercepted I/O requestfrom tapping driver 150. VDSA 160 makes up to three copies of thereceived I/O requests, in order to perform a set of actions which enablethe one or more data services engines 170 to provide various services.

A first copy is stored in persistent storage, and used to providecontinuous data protection. Specifically, VDSA 160 sends the first copyto journal manager 250, for storage in a dedicated virtual disk 270.Since all I/O requests are journaled on virtual disk 270, journalmanager 250 provides recovery data services for virtual servers 110,such as restoring virtual servers 110 to an historical image. In orderto conserve disk space, hash generator 220 derives a one-way hash fromthe I/O requests. Use of a hash ensures that only a single copy of anyI/O request data is stored on disk.

An optional second copy is used for disaster recovery. It is sent viaTCP transmitter 230 to remote VDSA 260. As such, access to all data isensured even when the production hardware is not available, thusenabling disaster recovery data services.

An optional third copy is sent to data analyzer and reporter 240, whichgenerates a report with information about the content of the data. Dataanalyzer and reporter 240 analyzes data content of the I/O requests andinfers information regarding the data state of virtual servers 110.E.g., data analyzer and reporter 240 may infer the operating systemlevel and the status of a virtual server 110.

Reference is made to FIG. 3, which is a simplified block diagram of avirtual replication system, in accordance with an embodiment of thepresent invention. Shown in FIG. 3 is a protected site designated SiteA, and a recovery site designated Site B. Site A includes a hypervisor100A with three virtual servers 110A-1, 110A-2 and 110A-3, and a VDSA160A. Site A includes two physical disks 140A-1 and 140A-2. Site Bincludes a hypervisor 100B with a VDSA 160B. Site B includes twophysical disks 140B-1 and 140B-2. All or some of virtual servers 110A1,110A-2 and 110A-3 may be designated as protected. Once a virtual serveris designated as protected, all changes made on the virtual server arereplicated at the recovery site.

In accordance with an embodiment of the present invention, every writecommand from a protected virtual server in hypervisor 100A isintercepted by tapping driver 150 (FIG. 1) and sent asynchronously byVDSA 160A to VDSA 160B for replication, via a wide area network (WAN)320, while the write command continues to be processed by the protectedserver.

At Site B, the write command is passed to a journal manager 250 (FIG.2), for journaling on a Site B virtual disk 270 (FIG. 2). After everyfew seconds, a checkpoint is written to the Site B journal, and during arecovery one of the checkpoints may be selected for recovering to thatpoint. Additionally, checkpoints may be manually added to the Site Bjournal by an administrator, along with a description of the checkpoint.E.g., a checkpoint may be added immediately prior to an event takingplace that may result in the need to perform a recovery, such as aplanned switch over to an emergency generator.

In addition to write commands being written to the Site B journal,mirrors 110B-1, 110B-2 and 110B-3 of the respective protected virtualservers 110A-1, 110A-2 and 110A-3 at Site A are created at Site B. Themirrors at Site B are updated at each checkpoint, so that they aremirrors of the corresponding virtual servers at Site A at the point ofthe last checkpoint. During a failover, an administrator can specifythat he wants to recover the virtual servers using the latest data sentfrom the Site A. Alternatively the administrator can specify an earliercheckpoint, in which case the mirrors on the virtual servers 110B1,110-B-2 and 110B-3 are rolled back to the earlier checkpoint, and thenthe virtual servers are recovered to Site B. As such, the administratorcan recover the environment to the point before any corruption, such asa crash or a virus, occurred, and ignore the write commands in thejournal that were corrupted.

VDSAs 160A and 160B ensure write order fidelity; i.e., data at Site B ismaintained in the same sequence as it was written at Site A. Writecommands are kept in sequence by assigning a timestamp or a sequencenumber to each write at Site A. The write commands are sequenced at SiteA, then transmitted to Site B asynchronously, then reordered at Site Bto the proper time sequence, and then written to the Site B journal.

The journal file is cyclic; i.e., after a pre-designated time period,the earliest entries in the journal are overwritten by the newestentries.

It will be appreciated by those skilled in the art that the virtualreplication appliance of the present invention operates at thehypervisor level, and thus obviates the need to consider physical disks.In distinction, conventional replication systems operate at the physicaldisk level. Embodiments of the present invention recover write commandsat the application level. Conventional replication systems recover writecommands at the SCSI level. As such, conventional replication systemsare not fully application-aware, whereas embodiment of the presentinvention are full application-aware, and replicate write commands froman application in a consistent manner.

The present invention offers many advantages.

-   -   Hardware Agnostic: Because VDSA 160 manages recovery of virtual        servers and virtual disks, it is not tied to specific hardware        that is used at the protected site or at the recovery site. The        hardware may be from the same vendor, or from different vendors.        As long as the storage device supports the iSCSI protocol, any        storage device, known today or to be developed in the future,        can be used.    -   Fully Scalable: Because VDSA 160 resides in the hypervisor        level, architectures of the present invention scale to multiple        sites having multiple hypervisors, as described hereinbelow with        reference to FIG. 4.    -   Efficient Asynchronous Replication: Write commands are captured        by VDSA 160 before they are written to a physical disk at the        protected site. The write commands are sent to the recovery site        asynchronously, and thus avoid long distance replication        latency. Moreover, only delta changes are sent to the recovery        site, and not a whole file or disk, which reduces the network        traffic, thereby reducing WAN requirements and improving        recovery time objective and recovery point objective.    -   Control of Recovery: An administrator controls when a recovery        is initiated, and to what point in time it recovers.    -   Near-Zero Recovery Point Objective (RPO): VDSA 160 continuously        protects data, sending a record of every write command        transacted at the protected site to the recovery site. As such,        recovery may be performed within a requested RPO.    -   Near-Zero Recovery Time Objective (RTO): During recovery the        mirrors of the protected virtual servers are recovered at the        recovery site from VDSA 160B, and synchronized to a requested        checkpoint. In accordance with an embodiment of the present        invention, during synchronization and while the virtual servers        at the recovery site are not yet fully synchronized, users can        nevertheless access the virtual servers at the recovery site.        Each user request to a virtual server is analyzed, and a        response is returned either from the virtual server directly, or        from the journal if the information in the journal is more        up-to-date. Such analysis of user requests continues until the        recovery site virtual environment is fully synchronized.    -   WAN Optimization between Protected and Recovery Sites: In        accordance with an embodiment of the present invention, write        commands re compressed before being sent from VDSA 160A to VDSA        160B, with throttling used to prioritize network traffic. As        such, communication between the protected site and the recovery        site is optimized.    -   WAN Failover Resilience: In accordance with an embodiment of the        present invention, data is cached prior to being transmitted to        the recovery site. If WAN 320 goes down, the cached data is        saved and, as soon as WAN 320 comes up again, the data is sent        to the recovery site and both sites are re-synchronized.    -   Single Point of Control: In accordance with an embodiment of the        present invention, both the protected and the recovery site are        managed from the same client console.

As indicated hereinabove, the architecture of FIG. 1 scales to multiplesites having multiple hypervisors. Reference is made to FIG. 4, which isa simplified block diagram of a cross-host multiple hypervisor system300 that includes data services managers for multiple sites that havemultiple hypervisors, in accordance with an embodiment of the presentinvention. The architecture of FIG. 4 includes three sites, designatedSite A, Site B and Site C, the three sites being communicatively coupledvia a network 320. Each site includes one or more hypervisors 100.Specifically, Site A includes three hypervisors, 100A/1, 100A/2 and100A/3, Site B includes two hypervisors, 1006/1 and 100B/2, and Site Cincludes one hypervisor 100C/1. The sites have respective one or morephysical disks 140A, 140B and 140C.

The hypervisors are shown in system 300 with their respective VDSA's160A/1, 160A/2, . . . , and the other components of the hypervisors,such as the virtual servers 110 and virtual disks 120, are not shown forthe sake of clarity. An example system with virtual servers 110 is shownin FIG. 7, and described hereinbelow.

The sites include respective data services managers 310A, 310B and 310Cthat coordinate hypervisors in the sites, and coordinate hypervisorsacross the sites.

The system of FIG. 4 may be used for data replication, whereby data atone site is replicated at one or more other sites, for protection. Thesolid communication lines 330 in FIG. 4 are used for in-site traffic,the dashed communication lines 340 are used for replication trafficbetween sites, and the dotted communication lines 350 are used forcontrol traffic between data services managers.

Data services managers 310A, 310B and 310C are control elements. Thedata services managers at each site communicate with one another tocoordinate state and instructions. The data services managers track thehypervisors in the environment, and track health and status of the VDSAs160A/1, 160A/2, . . . .

It will be appreciated by those skilled in the art that the environmentshown in FIG. 4 may be re-configured by moving one or more virtualservers 110 from one hypervisor 100 to another, by moving one or morevirtual disks 120 from one hypervisor 100 to another, and by adding oneor more additional virtual servers 110 to a hypervisor 100.

In accordance with an embodiment of the present invention, the dataservices managers enable designating groups of specific virtual servers110, referred to as virtual protection groups, to be protected. Forvirtual protection groups, write order fidelity is maintained. The dataservices managers enable designating a replication target for eachvirtual protection group; i.e., one or more sites, and one or morehypervisors in the one or more sites, at which the virtual protectiongroup is replicated. A virtual protection group may have more than onereplication target. The number of hypervisors and virtual servers withina virtual protection group and its replication target are not requiredto be the same.

Reference is made to FIG. 5, which is a user interface screenshot ofbi-directional replication of virtual protection groups, in accordancewith an embodiment of the present invention. Shown in FIG. 4 are virtualprotection groups 301 (“Exchange”), 302 (“WebApp”), 303 (“Dummy-R1”),304 (“Windows 2003”) and 305 (“Dummies-L”). Arrows 306 indicatedirection of replication.

Reference is made to FIG. 6, which is a user interface screenshot ofassignment of a replication target for a virtual protection group, inaccordance with an embodiment of the present invention. Shown in FIG. 6is an entry 307 for designating a recovery host, and an entry 308 fordesignating a recovery datastore for virtual protection group 304(“Windows 2003”) of FIG. 5. Respective source and target datastores,[SAN ZeRTO-30] 309A and [datastore1] 309B, are shown as being paired.

More generally, the recovery host may be assigned to a cluster, insteadof to a single hypervisor, and the recovery datastore may be assigned toa pool of resources, instead of to a single datastore. Such assignmentsare of particular advantage in providing the capability to recover datain an enterprise internal cloud that includes clusters and resourcepools, instead of using dedicated resources for recovery.

The data services managers synchronize site topology information. Assuch, a target site's hypervisors and datastores may be configured froma source site.

Virtual protection groups enable protection of applications that run onmultiple virtual servers and disks as a single unit. E.g., anapplication that runs on virtual servers many require a web server and adatabase, each of which run on a different virtual server than thevirtual server that runs the application. These virtual servers may bebundled together using a virtual protection group.

Referring back to FIG. 4, data services managers 310A, 310B and 310Cmonitor changes in the environment, and automatically update virtualprotection group settings accordingly. Such changes in the environmentinclude inter alia moving a virtual server 110 from one hypervisor 100to another, moving a virtual disk 120 from one hypervisor 100 toanother, and adding a virtual server 110 to a hypervisor 100.

For each virtual server 110 and its target host, each VDSA 160A/1,160A/2, . . . replicates IOs to its corresponding replication target.The VDSA can replicate all virtual servers to the same hypervisor, or todifferent hypervisors. Each VDSA maintains write order fidelity for theIOs passing through it, and the data services manager coordinates thewrites among the VDSAs.

Since the replication target hypervisor for each virtual server 110 in avirtual protection group may be specified arbitrarily, all virtualservers 110 in the virtual protection group may be replicated at asingle hypervisor, or at multiple hypervisors. Moreover, the virtualservers 110 in the source site may migrate across hosts duringreplication, and the data services manager tracks the migration andaccounts for it seamlessly.

Reference is made to FIG. 7, which is an example an environment forsystem 300, in accordance with an embodiment of the present invention.As shown in FIG. 7, system 300 includes the following components.

Site A

Hypervisor 100A/1: virtual servers 110A/1-1, 110A/1-2, 110A/1-3.Hypervisor 100A/2: virtual servers 110A/2-1, 110A/2-2, 110A/2-3.Hypervisor 100A/3: virtual servers 110A/3-1, 110A/3-2, 110A/3-3.

Site B

Hypervisor 100B/1: virtual servers 110B/1-1, 110B/1-2, 110B/1-3.Hypervisor 100B/2: virtual servers 110B/2-1, 1106/2-2, 110B/2-3.

Site C

Hypervisor 100C/1: virtual servers 110C/1-1, 110C/1-2, 110C/1-3,110C/1-4.

As further shown in FIG. 7, system 300 includes the following virtualprotection groups. Each virtual protection group is shown with adifferent hatching, for clarity.

VPG1 (shown with upward-sloping hatching)

-   -   Source at Site A: virtual servers 110A/1-1, 110A/2-1, 110A/3-1    -   Replication Target at Site B: virtual servers 110B/1-1,        110B/1-2, 110B/2-1        VPG2 (shown with downward-sloping hatching)    -   Source at Site B: virtual servers 1106/1-3, 110B/2-2    -   Replication Target at Site A: virtual servers 110A/1-2, 110A/2-2        VPG3 (shown with horizontal hatching)    -   Source at Site A: virtual server 110A/3-3    -   Replication Target at Site B: virtual serer 110B/2-3    -   Replication Target at Site C: virtual server 110C/1-4        VPG4 (shown with vertical hatching)    -   Source at Site A: virtual servers 110A/1-3, 110A/2-3, 110A/3-2    -   Replication Target at Site C: virtual servers 110C/1-1,        110C/1-2, 110C/1-3

As such, it will be appreciated by those skilled in the art that thehypervisor architecture of FIG. 1 scales to multiple host sites, each ofwhich hosts multiple hypervisors. The scaling flexibly allows fordifferent numbers of hypervisors at different sites, and differentnumbers of virtual services and virtual disks within differenthypervisors.

The present invention may be implemented through an applicationprogramming interface (API), exposed as web service operations.Reference is made to Appendices I-V, which define an API for virtualreplication web services, in accordance with an embodiment of thepresent invention.

In the foregoing specification, the invention has been described withreference to specific exemplary embodiments thereof. It will, however,be evident that various modifications and changes may be made to thespecific exemplary embodiments without departing from the broader spiritand scope of the invention as set forth in the appended claims.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

1.-20. (canceled)
 21. A system to manage cross-site hypervisors,comprising: a hypervisor at a first site, comprising: a virtual serverto make an input/output (I/O) request via an I/O data path; a virtualdisk to be read and written to using the I/O request; a tapping driverhaving visibility to the I/O data path to intercept the I/O request; avirtual data services appliance residing outside the I/O data path incommunication with the tapping driver to asynchronously receive the I/Orequest and provide data services based on the I/O request; and thetapping driver to cause the I/O request to be forwarded along the I/Odata path to the virtual disk and to separately cause the I/O request tobe forwarded, concurrent to the forwarding along the I/O data path, tothe virtual data services appliance; and a data services manager at thefirst site to coordinate the data services at the first site.
 22. Thesystem of claim 21, comprising the virtual data services appliance ofthe hypervisor to provide a copy of the I/O request to a journal managerat the first site.
 23. The system of claim 21, comprising the virtualdata services appliance of the hypervisor to transmit a copy of the I/Orequest to a virtual data services appliance at a second site,
 24. Thesystem of claim 21, comprising the virtual data services appliance ofthe hypervisor to provide a copy of the I/O request to a data analyzerat the first site.
 25. The system of claim 21, comprising the dataservices manager at the first site to coordinate the hypervisor at thefirst site with a data services manager at a second site coordinating ahypervisor at a second site.
 26. The system of claim 21, comprising thedata services manager at the first site to enable designating thevirtual server at the first site as a protection group to protect I/Oorder fidelity.
 27. The system of claim 21, comprising the data servicesmanager at the first site to manage migration of the virtual server fromthe first site to a second site during replication.
 28. A hypervisor,comprising: a virtual server at a first site to make an input/output(I/O) request via an I/O data path; a virtual disk at the first site tobe read and written to using the I/O request; a tapping driver at thefirst site having visibility to the I/O data path to intercept the I/Orequest; a virtual data services appliance at the first site, thevirtual data services appliance residing outside the I/O data path incommunication with the tapping driver to asynchronously receive the I/Orequest and provide data services based on the I/O request; the tappingdriver to cause the I/O request to be forwarded along the I/O data pathto the virtual disk and to separately cause the I/O request to beforwarded, concurrent to the forwarding along the I/O data path, to thevirtual data services appliance; and the virtual data services appliancein communication with a data services manager at the first site tocoordinate the data services.
 29. The hypervisor of claim 28, comprisingthe virtual data services appliance of the hypervisor to provide a copyof the I/O request to a journal manager at the first site.
 30. Thehypervisor of claim 28, comprising the virtual data services applianceof the hypervisor to transmit a copy of the I/O request to a virtualdata services appliance at a second site.
 31. The hypervisor of claim28, comprising the virtual data services appliance of the hypervisor toprovide a copy of the I/O request to a data analyzer at the first site.32. The hypervisor of claim 28, comprising the virtual data servicesappliance in communication with the data services manager to coordinatedata transfer from the first site to a second site.
 33. The hypervisorof claim 28, comprising the virtual data services appliance incommunication with the data services manager to provide a health andstatus of the virtual data services appliance.
 34. The hypervisor ofclaim 28, comprising a data services engine to provide the data servicesbased on a set of actions performed using a copy of the I/O requestgenerated by the virtual data services appliance asynchronously toprocessing of the I/O request in the I/O data path.
 35. A method ofmanaging cross-site hypervisors, comprising: intercepting, by a tappingdriver at a first site, an input/output (I/O) request sent by a virtualserver via an I/O data path to virtual disk, the tapping driver havingvisibility to the I/O data path; asynchronously receiving, by a virtualdata services appliance residing outside the I/O data path the firstsite, the I/O request and provide data services based on the I/Orequest; and causing, by the tapping driver, the I/O request to beforwarded along the I/O data path to the virtual disk and to separatelycause the I/O request to be forwarded, concurrent to the forwardingalong the I/O data path, to the virtual data services appliance; andcoordinating, by a data services manager at the first site, the dataservices at the first site.
 36. The method of claim 35, comprisingproviding, by the virtual data services appliance, copy of the I/Orequest to a journal manager at the first site.
 37. The method of claim35, comprising transmitting, by the virtual data services appliance, acopy of the I/O request to a virtual data services appliance at a secondsite.
 38. The method of claim 35, comprising providing, by the virtualdata services appliance, a copy of the I/O request to a data analyzer atthe first site.
 39. The method of claim 35, comprising providing, by thevirtual data services appliance, a health and status of the virtual dataservices appliance to the data services manager.
 40. The method of claim35, comprising assigning, by the data services manager at the firstsite, the virtual server at the first site as a protection group toprotect I/O order fidelity.